Because of a problem related to memory mapping, unexpected behavior might occur when you execute long-running SAS^® processes that use DS2 or any of the following SAS procedures and interfaces:

 

Product	Procedures and Interfaces
Base SAS®	DATA step, Macro, PROC FCMP, PROC PROTO, PROC SQL, WHERE statement
SAS/ETS® software	HPF Solution, PROC MODEL, PROC SEVERITY, PROC SIMILAR, PROC VARMAX
SAS/OR® software	PROC GA, PROC OPTMODEL, PROC NLP
SAS® Risk Dimensions®	PROC COMPILE, PROC MONTE, RISK Dimensions Solutions
SAS Solutions	EM Credit Scoring Nodes (for data flow analysis), PROC SVM, PROC TRANASSIGN
SAS/STAT® software	PROC CALIS, PROC GENMOD, PROC GLIMIX, PROC MCMC, PROC NLIN, PROC NLMIXED, PROC PHREG, PROC QUANTREG

 

The issue can manifest itself in a number of different ways, including system call failures or an unresponsive (hung) SAS process.

To help determine whether you are experiencing this issue, check to see whether your SAS process is exceeding the MAX_MAP_COUNT system limit. MAX_MAP_COUNT is the maximum number of memory map areas that a process can have. To check this limit on your system, execute the following command from the OS command line:

To verify that your SAS process is reaching the limit, determine how many maps the process is currently using by executing the following command (before killing an unresponsive process):

In this command, sas-pid specifies the process ID of the SAS process.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	Base SAS	64-bit Enabled AIX	9.4_M3	9.4_M5	9.4 TS1M3	9.4 TS1M5
		64-bit Enabled Solaris	9.4_M3	9.4_M5	9.4 TS1M3	9.4 TS1M5
		HP-UX IPF	9.4_M3	9.4_M5	9.4 TS1M3	9.4 TS1M5
		Linux for x64	9.4_M3	9.4_M5	9.4 TS1M3	9.4 TS1M5
		Solaris for x64	9.4_M3	9.4_M5	9.4 TS1M3	9.4 TS1M5

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

A fix for this issue for SAS Federation Server 4.2 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/Y46.html#60676

---

The problem is related to memory mapping. The issue can manifest itself in a number of different ways, including system call failures or an unresponsive (hung) SAS® process. Unexpected behavior might occur with long-running processes that use DS2 or a subset of DATA step programming language

Type:	Problem Note
Priority:	high

Date Modified:	2020-11-10 09:07:51
Date Created:	2017-06-22 11:58:58